Skip to content

Issue 48864: Use CURRENT_TIMESTAMP instead of system time#7104

Merged
labkey-nicka merged 3 commits intodevelopfrom
fb_current_timestamp_deux
Oct 8, 2025
Merged

Issue 48864: Use CURRENT_TIMESTAMP instead of system time#7104
labkey-nicka merged 3 commits intodevelopfrom
fb_current_timestamp_deux

Conversation

@labkey-nicka
Copy link
Contributor

@labkey-nicka labkey-nicka commented Oct 6, 2025

Rationale

This addresses Issue 48864 and was spurred on by intermittent API test failures caused by discrepancies in server v. database time.

Related Pull Requests

Changes

  • Move marker interface NowTimestamp from StatementUtils to SQLFragment.
  • Introduce SQLFragment.appendValue(NowTimestamp)
  • Revise Table.insert() and Table.update() statement generation to use NowTimestamp.
  • Remove explicit created/createdBy value setting for new audit events. Let underlying statement generation handle that.

@labkey-nicka labkey-nicka self-assigned this Oct 6, 2025
@labkey-nicka labkey-nicka force-pushed the fb_current_timestamp_deux branch from 703fa23 to aaeb6b0 Compare October 6, 2025 23:01
@labkey-nicka labkey-nicka force-pushed the fb_current_timestamp_deux branch from aaeb6b0 to 5a43de1 Compare October 7, 2025 15:21
@labkey-nicka labkey-nicka merged commit aaf0332 into develop Oct 8, 2025
16 checks passed
@labkey-nicka labkey-nicka deleted the fb_current_timestamp_deux branch October 8, 2025 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants